What we have decided not to build
A short list, kept publicly, of the features we keep being asked for and keep saying no to — and why.
Every roadmap is mostly a list of things you said yes to. Ours has a second list, and we think it explains the product better than the first one does.
A chat inbox
People ask for messaging on the booking page so the two parties can talk before the meeting. We keep saying no. The point of a booking link is that the conversation about when does not happen. Adding a place for it to happen would rebuild the problem inside the fix.
Meeting recordings
We can attach a video room to a booking. We will not record what happens inside it. That is a different product with different obligations, and doing it badly is worse than not doing it.
Availability scoring
Several teams have asked for a ranking that nudges bookers toward the slots we would prefer. It works, briefly, and then people notice, and then they stop trusting the page. A calendar that quietly lies about what is free is not a calendar.
An analytics suite
You can export bookings and put them wherever your other numbers live. We are not going to build a second dashboard for you to ignore.